feat: Migrate sso resources from edp-install to gerrit-operator(#59) #60
+31
−6
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Description
This commit introduces new functionality to support external secrets for the KubeRocketCI Gerrit Operator. It adds configurations and templates for managing secrets using AWS or generic providers via the External Secrets Operator. Key features include the ability to configure secret providers, specify secret store names, and manage Keycloak integration for SSO.
Fixes # (issue)
Type of change
How Has This Been Tested?
The changes have been tested by deploying the updated Helm chart in a staging environment. The following tests were performed:
Verification of secret creation using both AWS Parameter Store and Secrets Manager.
Validation of Keycloak integration with the Gerrit SSO.
Ensured that existing deployments without external secrets continue to function without issues.
Steps to reproduce:
Deploy the updated Helm chart with externalSecrets.enabled set to true.
Configure the externalSecrets.type to either aws or generic.
Verify that the ExternalSecrets and SecretStores are created as expected.
Test the Keycloak SSO login flow.
Checklist: